Fix a rare crash in TSKSPKIHashCache#348
Open
fabianmuecke wants to merge 2 commits intodatatheorem:masterfrom
Open
Fix a rare crash in TSKSPKIHashCache#348fabianmuecke wants to merge 2 commits intodatatheorem:masterfrom
fabianmuecke wants to merge 2 commits intodatatheorem:masterfrom
Conversation
|
I do see the same issue in my project. What holds this pr back from merging? |
aztrmobile
approved these changes
Nov 12, 2025
|
Does anyone have a crash log they can share? :) Edit: oops, from #347: |
|
@NSExceptional -- here is another
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes #347 by adding a missing
dispatch_syncwhen reading the cache on the main dispatch queue to write it to the file system. This should be safe, as the onlydispatch_barrier_synccall does not access the main queue, so cannot cause a deadlock.I tried to find a test that would replicate the issue and found one, that will randomly (maybe once out of 1000 runs) achieve that. All attempts to improve the reliability of the test were futile. I added it the the PR anyway. Feel free to remove, if you think it's useless.